I’ve encountered two problems in Forza Motorsport that I hope the d-box team can take a look at, here’s the TLDR version:
- On launch, occasional laggy feeling to motion, not always but can happen ~50% of the time.
- Pitch throw is too short for the race car variants, on braking the system pitches forward but quickly hits a hard stop, very immersion-breaking.
For those with a bit more patience, here’s a more detailed description:
-
This isn’t new, it’s happened before in both iracing and AMS2, where sometimes the haptics feel fine but all motion is laggy and slow. Usually fixed on a restart or maybe a reboot. In FM though it’s happening a lot. I followed the profile instructions and launched the listener only after launching the game, which helped for a while but today it took me 4 reboots and a new USB port to resolve it. My best guess is that there’s some sort of USB system conflict but I’ve no idea how to diagnose that, maybe reinstalling windows will help to clear it out. Any tips would be welcome.
-
This one probably isn’t a bug, but it’s so immersion-breaking that I’m hoping something can be adjusted. Also worth mentioning that my system has 3” of travel, it could be that the 1.5” experience is different. If I pick a road car - any of them really, say a Mini - under braking the system pitches forward and if I modulate the brake the pitch will respond - a bit more, or less depending on brake pressure, until the car stops. That’s perfect and most sims work that way e.g. RF2, iracing, ACC. If instead I pick a racecar - for example a prototype (anything with a stiff suspension I presume) - under braking it pitches forward but very quickly reaches a stop and modulating brake pressure makes no difference. It could be a bug in the simulation where it runs out of suspension travel too quickly (there’s no way a real race car would fully compress suspension on mild braking). Reducing the pitch setting in game center helps to delay the hard stop effect but then you’re dialing out the effect which is unfortunate. As an aside, in AMS2 this happens with every car. I contacted d-box support a year ago with the AMS2 feedback and they said nothing could be done as it was a problem on the simulator side, not d-box.
Thanks for reading!